The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
billion-nextjs	Ready	Preview, Comment	Jul 28, 2026 7:04am

Deployment note: before enabling these scrapers in production, apply the included database migrations and ensure the scraper runtime has outbound network access to the official public source hosts. No new API keys are required; OPEN_STATES_API_KEY is optional for Texas Legislature identity matching.

Source inventory and app-presentation follow-up

Official sources added

• NCSBE: current-cycle candidate CSVs, referendum PDFs, and election-result ZIP/TSV files, with exact provenance and certification state.
• Texas SOS: structured Civix feeds for contests, candidates, propositions, county totals, turnout, reporting status, and outcomes.
• Texas Legislative Council: constitutional-amendment analysis PDFs with ballot language, neutral analysis, fiscal effects, and supporter/opponent arguments with page citations.
• Texas Legislature bulk service: current-session history XML and bill text, analyses, fiscal notes, sponsors, subjects, actions, documents, and published votes.
• Durham County Legistar: BOCC meetings, items, actions, documents, cancellations/revisions, and named votes.
• Durham OnBase: City Council meetings, agenda/minutes outlines, item detail, attachments, and official action text.
• Cedar Park CivicEngage/Municode: Council meetings, agendas, packets, minutes, motions/outcomes, and votes.

These are public official sources. Only POSTGRES_URL is required; OPEN_STATES_API_KEY is optional for Texas bill identity matching.

Backend and operations

This adds civic.getNcElectionData, civic.getTexasCurrentElection, content.texasBills, and provider-neutral localGovernment readers. The scrapers are registered in the CLI and all, but this PR does not deploy a production cron; continuous collection still needs scheduled jobs.

Current app integration: partial

Upcoming meetings use the new API, and Texas official measure data can enrich Civic measures at the API layer. However:

• Expo still explicitly blocks ballots outside California.
• NC/Texas election readers and content.texasBills have no direct Expo consumer.
• “Local Bills” still uses the older live Legistar route.
• Meeting cards link out instead of rendering stored agenda items/votes.
• Meetings are not scoped from the saved address.

Proposed presentation

1. Your Ballot: keep Google Civic for address resolution/ballot order, then merge matching official NC/Texas rows. Show source, freshness, certification, and field-level citations.
2. Results: only show the same election cycle/date; label unofficial vs. certified and reject stale results.
3. Your State Legislature: add a separate bills surface with session/chamber/status filters and detail for sponsors, actions, votes, text, analyses, and fiscal notes.
4. City & County Meetings: address-scope the jurisdiction and add a detail screen for agenda items, outcomes, named votes, and official documents.
5. Operations: schedule each source and expose last-success/freshness diagnostics.

Recommendation: keep state legislation and council agenda items as distinct destinations because their lifecycles and user expectations differ.